PVector's setHeading() highlighted #1007
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @SushantBansal-tech thank you for your effort, this PR contains a lot of changes not related to the actual fix, please clean those up. |
|
Actually, since you haven't been assigned the related issue, I'm going to close this PR for now. We're following the same contribution guidelines as p5.js — please wait for approval and assignment before starting work on a PR. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the issue where PVector.setHeading() was not being highlighted in the Processing editor.
Changes made:
Added setHeading_ to keywords.txt
Ensured it is categorized correctly for syntax highlighting
Issue reference:
Fixes #472 )
Testing:
Verified that setHeading() now appears highlighted in the editor
No breaking changes introduced